Repository navigation
ci: actions/checkout v7.0.1, on Node.js 24: v4.2.2 runs on Node.js 20, which GitHub has deprecated - #4
Merged
Conversation
…, which GitHub has deprecated
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
actions/checkoutv4.2.2 runs on Node.js 20, which GitHub has deprecated: every run warns, and it forces the action onto Node.js 24 already. v7.0.1 runs on Node.js 24 and is pinned by its commit, like every action here. The other pinned actions (cache,upload-artifact,download-artifact,setup-uv, lychee's composite action) already run on Node.js 24.The changes since v4 don't touch these workflows:
gitstill finds.pull_request_targetorworkflow_run, which no workflow here uses.The same change goes into overpressure, phoenix, packages, builder, linux and .github.
Checks
Hardware
Not needed. This PR's own run checks out with v7.0.1.